|
2024-01-30 15:00 developer |
|
|
|
Hello, Jason, Could you please provide the test result of swan? Thank you. Sangmin Choi. |
|
|
Hi Sangmin, Could you help me post it on Syanptics Jira? I'll push Syanptics China FAE to check it. Thanks, Jason |
|
|
Hello, Jason, I created the Synaptics jira. https://synacsm.atlassian.net/servicedesk/customer/portal/173/CSMSKBSBLT-234 Thank you. Sangmin Choi. |
|
|
Hi Jason I created the jira below. https://jira.skbroadband.com/browse/BTFAML-1395 I'll let you know if there's a feedback. Thank you YK.Jung |
|
|
Hi All, I've checked our all product ATV10~ATV12. all are fail Please check the following link https://android.googlesource.com/platform/libcore/+/1ea181fec2e2e0e95298c196193d6fa324d96db7/support/src/test/java/tests/resources/x509/cert-rsa-dates.txt The certificated was expired in recently day. Now, there is a pass method to pass it Modify STB date to 1/26, we can pass it. I am trying to convince our 3PL to do it. This method only works in VTS tool (GSI image), when test with CTS, the tool will auto turn on "automatic date & time" (if you off it before), so CTS will still fail But for the next FW It looks like we should patch this file to update certificate in FW. As you know, Google no longer maintain ATV10. so I don't know how to patch it. For ATV12, I think we can wait for Google official patch. For ATV10, I think we need the Soc vendor suggestion. Thanks, Jason |
|
|
Hi YK, It looks like we should backport it https://android.googlesource.com/platform/libcore/+/1ea181fec2e2e0e95298c196193d6fa324d96db7 Please ask AML KR to review it. Thanks Jason |
|
|
Hi Jason The feedback of amlogic is as follows ==================================================================== Google's test certificate certification expires on 1.26, so tests after 1.26 will fail. libcore/support/src/test/java/tests/resources/x509/cert-rsa-dates.txt notBefore=Jan 28 21:42:14 2014 GMT notAfter=Jan 26 21:42:14 2024 GMT Please update and test the date as below. https://android.googlesource.com/platform/libcore/+/1ea181fec2e2e0e95298c196193d6fa324d96db7/support/src/test/java/tests/resources/x509/cert-rsa-dates.txt ==================================================================================================== Please check it Thank you YK.Jung image.png (27,992 bytes) |
|
|
Hi YK, I've patched the following patch yesterday night. https://android.googlesource.com/platform/libcore/+/1ea181fec2e2e0e95298c196193d6fa324d96db7 But the result is still fail. I just want to know if this failure should be fix on both side (FW and test tool) If this failure should also be addressed on tool side, even we applied the patch, we still can not pass it. Please check it with Amlogic. And as you know, Google no longer maintain ATV10. so there is no ATV10 daily build tool and fresh GSI image. so we will still encounter this issue on ATV10 Thanks, Jason |
|
|
Hi Jason Please check it again after updating the test tool. Thank you YK.Jung image-2.png (102,276 bytes) image-3.png (86,334 bytes) |
|
|
Hi YK, I need to correct my comment. >>This method only works in VTS tool (GSI image), when test with CTS, the tool will auto turn on "automatic date & time" (if you off it before), so CTS will still fail. This is wrong, there is an app that always turn on "automatic date & time" when we off it in our other project. Now, the test method is turning off "automatic date & time" an setting date to 1/26. Then we can pass CTS/CTS-ON-GSI test_Provider case. And I've confirmed it again. Even if we applied the following patch (update the certificated) https://android.googlesource.com/platform/libcore/+/1ea181fec2e2e0e95298c196193d6fa324d96db7 we still can NOT pass this case. so in my current opinion, I think AML should check if this failure should be addressed on both side (FW and test tool) For ATV12. I think Google will release new patch and new tool to address it. For ATV10, Google no longer maintain it. CTS: Even though we patched it, there are still issues with the testing tool, so we will still fail on this case. CTS-ON-GSI: the GSI image is released by Google, so we can not patch it. but Google no longer maintain ATV10 GSI, and Google also no longer maintain ATV10 VTS tool, so we will still fail on this case. Conclusion: if AML think this failure must be fixed on both side. Could AML discuss it with Google if we can get waiver for ATV10 project. Thanks, Jason |
|
|
Hi YK, I just saw Google updated the daily build tool. I will check if this failure should be fixed on 1. FW side 2. tool side 3. both side. Thanks, Jason |
|
|
Hi all, I've checked it with SWAN (CTS) It seems that this failure must be solved from the tool side. Thanks, Jason test.jpg (84,095 bytes) |
|
|
Hello, Jason, So, can we close the SoC issue ticket? Thank you. Sangmin Choi. |
|
|
Hi Sangmin, No problem. I'll close it. Thanks, Jason |
- yk.jung ( (ALTech) Younkwang Jung ) developer
.png)
.png)
.png)
